Managing group authority and access to a secured file system in a decentralized environment

ABSTRACT

Presented here is a system that manages secured file system, and an authority to the secured file system, by granting access only to a user who is authorized to access the file system. The user within the system is identified using a unique key unique to each user. The user&#39;s authority is recorded in a linear sequence distributed among multiple devices each of which independently verifies the validity of each block in the linear sequence. The validity of the linear sequence is guaranteed by preventing certain operations from being performed on the linear sequence, such as branching of the linear sequence, deletion, and modification of the blocks within the linear sequence. Prior to adding a new block to the linear sequence, the validity of the block is independently computed by each of the devices.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is a continuation of U.S. patent applicationSer. No. 16/709,509, filed Dec. 12, 2019, which claims priority to andbenefit of U.S. Provisional Patent Application Nos. 62/778,633, filedDec. 12, 2018 and 62/830,002, filed Apr. 5, 2019, each of which ishereby incorporated by reference in its entirety.

TECHNICAL FIELD

The present application is related to managing access to a secured filesystem, and more specifically, to methods and systems that manage groupauthority and access to the secured file system in a decentralizedenvironment.

BACKGROUND

The major problem our computing systems face today is that internalthreats—that is, threats from our reliance upon a centralizedinfrastructure and the people that manage and provide it—are a part ofthe overall threat model. According to Microsoft SharePoint Admin Roledocumentation, “[g]lobal admins and SharePoint admins don't haveautomatic access to all sites and each user's OneDrive, but they cangive themselves access to any site or OneDrive.” Our current approach toinfrastructure, that centralizes the management and provision ofsecurity and access control with admins allows people access toinformation without a need-to-know that information. As a result,administrators that do not have the authority to read data stored on theserver that they are administering can still gain access and read thedata, without the authority to do so.

SUMMARY

Presented here is a system that manages file system, and an authority toaccess the file system, by granting access only to a user who isauthorized to access the file system. Access granted to the user cannotexceed the authority of the user. The user within the system isidentified using a cryptographic key unique to each user. The user'sauthority is recorded in a linear sequence, akin to a block chain, whichis distributed among multiple devices. Each of the multiple devicesindependently verifies the validity of each block in the linearsequence, thus preventing a compromised central server from grantingunauthorized access. The validity of the linear sequence is guaranteedby preventing certain operations from being performed on the linearsequence, such as branching of the linear sequence, deletion of theblocks within the linear sequence, and modification of the blocks withinthe linear sequence. Prior to adding a new block to the linear sequence,the validity of the block is independently computed by each of thedevices in the system to ensure that the user requesting the addition ofthe block has the authority to add the block to the linear sequence, andmore specifically, to perform the operation specified by the contents ofthe block.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows a system to manage group authority and access tocryptographically secure data in a decentralized environment.

FIG. 2 shows a team linear sequence and a space linear sequence.

FIG. 3 shows the linear ordering between a team linear sequence and aspace linear sequence.

FIG. 4 shows anatomy of a block.

FIG. 5 shows verification of various layers of policies that can existwithin the system.

FIG. 6 shows various cryptographic IDs that can exist within the system.

FIG. 7 shows how a block can be distributed to multiple devices.

FIG. 8 shows a linear sequence containing blocks.

FIG. 9 shows a team linear sequence and a space linear sequence.

FIGS. 10A-B show authority computation in case a malicious actor triesto infiltrate the system.

FIGS. 11A-C show how access to encrypted data can be controlled uponauthority revocation.

FIG. 12 is a flowchart of a method to manage authority, via adistributed ledger, separately from access to encrypted data by one ormore trusted devices, wherein each of the trusted devices corresponds toat least one cryptographic key-based identity.

FIG. 13 is a flowchart of a method to manage access to encrypted datausing a distributed ledger.

FIG. 14 is a diagrammatic representation of a machine in the exampleform of a computer system within which a set of instructions, forcausing the machine to perform any one or more of the methodologies ormodules discussed herein, may be executed.

DETAILED DESCRIPTION Managing Group Authority and Access to Secure Datain a Decentralized Environment

FIG. 1 shows a system to manage group authority and access tocryptographically secure data in a decentralized environment. The server100 is in communication with multiple devices 110, 120, 130, 140, 150,also called endpoints. Each of the devices 110-150 can be associatedwith an entity or a user such as Alice, Bob, Carol, Dave, Ellen,respectively. Each user Alice-Ellen can have a unique cryptographic useridentification (“ID”), as explained later in this application, and eachdevice can have a unique cryptographic device ID. Each cryptographicuser ID can have one or more cryptographic device IDs associated withit.

The unique cryptographic user IDs can be separated into teams, such asteam 1 and team 2 as shown in FIG. 1. For example, Alice's, Bob's andCarol's cryptographic user IDs can be members of team 1, while Dave'sand Ellen's cryptographic user IDs can be members of team 2, as shown inFIG. 1. Team 1 and team 2 can have mutually exclusive membership, asshown in FIG. 1, or can have partially overlapping membership. The teammembership can be recorded in a linear sequence, for example, a teamlinear sequence 160, 170 (only one instance of a team linear sequencelabeled for brevity). Each team 1, 2 can have one team linear sequence160, 170, respectively. The linear sequence, such as the team linearsequence 160, 170 and a space linear sequence 190, 192, 194, is acryptographic data structure akin to a ledger. Because the linearsequence can be distributed across multiple devices, each of whichindependently verifies the linear sequence, the linear sequence canrepresent a distributed ledger.

Each team 1, 2 can have one or more spaces 180, 182, 184 (only oneinstance of a space labeled for brevity). Each space 180, 182, 184 canbe a virtual compartment containing encrypted data and members havingaccess to the encrypted data. A subset of team members can be includedin one or more spaces 180, 182, 184 and given authority to accessencrypted data associated with the one or more spaces 180, 182, 184. Forexample, team 1 has space 180, and all the team members Alice, Bob andCarol are invited to space 180. In another example, team 2 has space 182and 184. Space 182 only has Dave as a member, while space 184 has bothDave and Ellen as members. Each space 180, 182, 184 can have encrypteddata that can be made accessible only to the space members. Encrypteddata can include content or data, or both. For example, encrypted datacan include a file, a file system, a document, and/or messages such asinstant messages, emails, chat messages, text messages, etc.

In an example, only users Alice, Bob, Carol have authority to theencrypted data associated with space 180. In another example, only userDave has the authority to the encrypted data associated with the space182, while both users Dave and Ellen have the authority to accessencrypted data associated with space 184. Authority to the encrypteddata can include permission to read, write, and/or modify the encrypteddata. Access to encrypted data can be granted upon verifying that thecryptographic user ID requesting the access has the authorityencompassing the access.

For example, user Ellen's cryptographic user ID can have the authorityto read the encrypted data. However, if user Ellen's cryptographic userID requests to write to the encrypted data, user Ellen's cryptographicuser ID will be denied the access to write to the encrypted data becauseuser Ellen's cryptographic user ID lacks the authority. In other words,in the system disclosed here, the access to the encrypted data cannotexceed the authority associated with the encrypted data.

In another embodiment, the teams 1, 2 do not exist, and the users can begrouped into one or more spaces 180, 182, 184. To generate a space, ageneral pool of cryptographic user IDs that exist in the system can besearched to define the members of the space. The team linear sequence160, 170 can be integrated into the corresponding space linear sequence190, 192, 194 (only one instance of a space linear sequence labeled forbrevity). For example, the space linear sequence 190 can include theteam linear sequence 160 and the space linear sequence 192, the spacelinear sequence 192 can include the team linear sequence 170 and thespace linear sequence 192, while the space linear sequence 194 caninclude the team linear sequence 170 and the space or list 194.

A record of the authority associated with the encrypted data can becomputed by combining the team linear sequence 160, 170 and acorresponding space linear sequence 190, 192, 194, as described furtherin this application. In addition to storing authority and membership,the space linear sequence 190, 192, 194 can also store the encrypteddata and/or references to the encrypted data.

A copy of the team linear sequence 160, 170 and the space linearsequence 190, 192, 194 can be distributed to all the devices 110-160whose cryptographic user IDs are members of the corresponding team andspace as well as the server 100. For example, devices 110-130 have acopy of the team linear sequence 160 and the space linear sequence 190because the cryptographic user IDs associated with the devices 110-130are members of team 2 and space 180. In another example, device 140 hasa copy of the team linear sequence 170 and space linear sequences 192and 194, because user Dave's cryptographic user ID associated with thedevice 140 is a member of team 2 and space 182, 184. In a third example,device 150 has a copy of the team linear sequence 170 and space linearsequence 194, because user Ellen's cryptographic user ID associated withdevice 150 is a member of team 2 and space 184.

The metadata contained in the team linear sequence 160, 170 and thespace linear sequence 190, 192, 194 can be stored in plain text, whilethe remainder of the data can be encrypted. The metadata can includeauthority information, policy information, roles, etc., stored withinthe team linear sequence 160, 170 and the space linear sequence 190,192, 194. The remainder of the data can include confidential data suchas files, filesystems, messages, and/or other confidential data. Forexample, filenames can be a part of the confidential data if theencrypted data includes files and/or filesystems. The filesystems,files, and/or messages can only be accessed by knowing the encryptionkey used in encrypting the data. Even if an attacker were tosuccessfully gain control of the encryption key, a user's private key,and/or authorized endpoint device, the compromise of the system would belimited.

For example, if the attacker gains control of the encryption keyassociated with space 182, the attacker would only be able to accessconfidential data within the space 182, not the confidential data withinspaces 184 and 180. If an attacker obtains Ellen's private key, theattacker would only be able to access confidential data within the space184, and not spaces 180 and 182. Thus, by compartmentalizing authorityand access to spaces 180, 182, 184, the breach of the system can beconfined.

FIG. 2 shows a team linear sequence and a space linear sequence. A teamlinear sequence 200 can be used to track identities of team members andtheir authority in a team. A space linear sequence 210 can be used toform a secure compartment which can admit a subset of the team members.The secure compartments are used to manage data and negotiate sharedkeys among the space members. The team linear sequence 200 can beconnected to a program 220 containing a system policy, as well as to adatabase 230 containing facts. The space linear sequence 210 can rely onthe team linear sequence 200 to determine policy within the space. Thespace linear sequence 210 can be connected to a database 250 containingfacts.

The team linear sequence 200 and the space linear sequence 210 can eachcontain multiple blocks 205, 207, 209, 215 (only 4 labeled for brevity).The initial block 205 of the team linear sequence 200 can define apolicy for the team. A policy can specify a role and an authorityassociated with the role. For example, a policy can specify “onlyadministrators can create spaces within a team.” A team policy can beobtained from a policy template stored in a policy database and/or canbe modified when instantiating the first block 205. Alternatively, thefirst block 205 can define the team policy without reference to thepolicy template. A policy program 220 can be shared between differentteams. The different teams, however, can have different fact databases230. The team policy can also be modified by later blocks added to theteam linear sequences 200, if the team policy defining block 205 permitsmodification.

The policy program 220 can store policy templates that can be includedand/or modified as policy in the initial block 205. The fact database230 can contain unique key-value pairs that can define user and userauthority within the system. For example, a key-value pair that can beadded to the fact database 200 can be “Alice-administrator”, after ablock that specifies that Alice is an administrator has been verified.

Block 207 of the team linear sequence 200 can include a profile of theuser that is a member of the team 200. The user profile can include theuser's identity 240 which can be represented by a cryptographic user ID,such as a public-key in an asymmetric cryptographic algorithm such asRivest-Shamir-Adleman (RSA) or Diffie Hellman (DH). Only the user can bein possession of the private-key. The user profile can also include acryptographic device ID 242, 244 associated with all the devices thatthe user has approved.

There are multiple ways that a device can be added to the system. Forexample, the user can approve the device by sending a request to add thedevice to the system, where the request is signed with a private key ofthe user. In another example, to approve a device, the user can performa multi-step process. In the first step, the user can create a new setof device keys using the asymmetric cryptographic algorithm. In thesecond step, the user can sign the device keys with the user's privatekey and construct a device certificate containing the device public-keyand the user's private key signatures. In the third step, the device cansend a request, which includes the certificate from the second step, tobe added to the team, where the request is signed using the deviceprivate key. The system can authenticate that a team member has made therequest by verifying the request using the public-key of the user. Thecryptographic device ID can be a cryptographic hash of the public-key ofthe asymmetric cryptographic algorithm, while the private-key can beknown only to the device and can be used to authenticate actionsperformed by the device.

Block 209 of the team linear sequence 200 can include an event such asaddition of a new user, creation of the space linear sequences 210, achange to policy 205, removal of an existing user, and/or a change ofrole of a user.

Block 215 of the space linear sequence 210 can include an event such asaddition of a user to the space, addition of encrypted data to thespace, removal of a user from space, etc. Each event 215 in the spacelinear sequence 210 complies with the policy defined in the team linearsequence 200. In some embodiments, policy cannot be changed in the spacelinear sequence 210 and must be changed in the team linear sequence 200.A team can have multiple spaces with different policies by definingmultiple space types having different policies, and establishing thespaces corresponding to the different space types. For example, a spacetype can include an “administrator space type” where all users haveadministrator roles and administrators add and remove other users andcan have read and write access to the encrypted data. In anotherexample, the space type can include “stratified space type” where someusers have administrator roles, and some users have user roles, and theadministrator roles have more authority than the user roles. Events inthe team linear sequence 210 that change authority of a user can bestored in the fact database 250.

User policy 205 can be defined to enable users matching certainattributes to only have access to the space linear sequence 210 andspace encrypted data for a limited amount of time. The passage of timecan be measured by an always increasing clock that can provide atimestamp 260, 270, 280, 290 for each block 215 in the space linearsequence 210. The timestamp 260 can, for example, state “11:46 AM Nov.21, 2019 (PST).” In the space linear sequence 210, the timestamp 260,270, 280, 290 is always increasing between subsequent blocks. To enabletime-limited access to the space linear sequence 210 and associatedencrypted data, the user policy 205 can state that “user associated withprofile 1 can have access to the linear sequence until Dec. 2, 2019.”

FIG. 3 shows the linear ordering between a team linear sequence and aspace linear sequence. Because the policy at least partially definingauthority is stored in the team linear sequence 310, to compute anauthority in a space linear sequence 300, a reference to the team linearsequence 310 needs to be made.

For example, in block 320 of the space linear sequence 300, the user ofthe space requests to add another user. In block 330 of the team linearsequence 310, the policy defined authority of the space user to addanother space user, however in block 340 of the team linear sequence310, the policy was modified to prevent space users from adding othersspace users. To determine whether block 320 is valid and should be addedto the space linear sequence 300, the linear sequence of blocks 330, 340in the team linear sequence 310 and the blocks 320, 350, 360 in thespace linear sequence 300 needs to be established.

To establish the linear sequence, a temporal relationship 370, 380, 390can be established between the blocks 320, 350, 360 in the space linearsequence 300 and the blocks 330, 340 in the team linear sequence 310.The temporal relationship 370, 380, 390 can include a pointer from thespace block 320, 350, 360 to the team block which is the immediatepredecessor or immediate successor of the space block 320, 350, 360. InFIG. 3, the temporal relationships 370, 380, 390 point from the spaceblock 320, 350, 360 to the immediately preceding team block. Forexample, temporal relationship 370, 380 indicates that the team block330 is the immediate predecessor of space blocks 320, 350, meaning thatspace blocks 320, 350 were created after the team block 330, but beforeteam block 340. Similarly, the temporal relationship 290 indicates thatspace block 360 was created after team block 340.

FIG. 4 shows anatomy of a block. The block 400, 410, can contain one ormore events 1-6. The events 1-6 in blocks 400, 410 can be atomic. Eachevent 1-6 is committed in a single block 400, 410.

A transaction can include one or more events where the last event issigned. A transaction can be produced by a single client, such as client110 in FIG. 1. When a transaction includes multiple events, such astransaction 1 containing events 1 and 2, the events can be ordered bythe client prior to being sent to the server. The ordering of the eventsis indicated using arrows 420, 430, 440, 450. Upon receivingtransactions 1-4 from multiple clients, the server can ordertransactions according to the order indicated by the arrows 420, 430,440, 450.

Events in a single transaction point to each other, and the last eventis signed. For example, events 1 and 2 form a single transaction 1.Similarly, events 5 and 6 form a single transaction 4. The arrow 420between event 3 and event 2, indicates that a server should commit event3 to the linear sequence after event 1. Similarly, the arrow 430 betweenevents 5 and 6 indicates that the server should commit the event 6 tothe linear sequence after event 5.

In an embodiment, events 1 and 2 come from a single client, while event3 can come from the same client as events 1 and 2, or from a differentclient. Similarly, events 5 and 6 come from a single client, while event4 can come from the same client or a different client. Further to thisembodiment, there can be at least one and up to four clients creatingtransactions 1-4, as shown in FIG. 4. For example, a single client canauthor transaction 1, including events 1 and 2. A second client canauthor transaction 2 including event 3. A third client can authortransaction 3 including event 4, and a fourth client can authortransaction 4 including events 5 and 6.

In the case that more than one event, for example, events 1-3, need tobe added in an atomic manner, the events 1-3 can be combined into asingle block 400, and the block 400 can be stored in the linearsequence. In the block 400, 410, only the last event, such as event 3,6, respectively, can be signed and none of the events 1-3, 4-6 in theblock 400, 410 are valid unless they all appear in the intended order inthe intended block.

The events 1-6 in blocks 400, 410 are cryptographically signed andrecorded in an authenticated linear sequence, as explained in thisapplication. The structure of the linear sequences guarantees thatdevices 110-160 in FIG. 1, which accept a block with some index n, arecertain to agree on the contents of all blocks with an index less thann. Blocks 400, 410 have indices 1, 2, respectively, in FIG. 4.

Once the block 400, 410 is finalized, the block 400, 410 gains a blockID. Finalizing a block means committing a block to a durable storage andnot changing the block. A block ID is a tuple of the block's index, andthe cryptographic hash of its contents. For a given block n, all eventsintended to be added to the linear sequence in block n+1 can includeblock ID of block n. This ensures that the intended ordering of eventsof devices 110-160 is preserved. Additionally, only devices which agreeon the block order and contents of blocks 0 through n, can accept anevent in block n+1.

FIG. 5 shows verification of various layers of policies that can existwithin the system. An events 500 is processed using a formal policywhich may either reject an event 500 or accept an event 500, andoptionally update a database of facts 510, 520. A fact database 510, 520is an index over the linear sequence with respect to the policy. Theindex is a collection of key value pairs. For example, the fact database510, 520 can record facts generated by the event 500 and the policy rulewhich authorized it. The fact database 510, 520 can be read by a policypressor when deciding if the event 500 is valid and should be acceptedin the linear sequence, such as a team linear sequence, or a spacelinear sequence.

When a server 100 in FIG. 1 receives the event 500, the server caninclude the event 500 in the next block. When the device 110-160receives the event 500, the device can process the event 500 based onthe business needs.

The system policy 530 is implemented by the device 110-160 and server100. All cooperating devices 110-160 must use the same system policy 530when processing the same block. In one embodiment, system policy 530 canbe implemented as source code in a programming language such as Rust,Python, Go, or a proprietary policy language. The system policy 530describes the structure of the blocks themselves. The system policy 530describes the core protocol of the linear sequences, such as “all eventsin block n must reference block n−1.”

The user policy 540 can be the team policy 205 in FIG. 2. The teampolicy 205 can be provided by a customer and can be tailored to thecustomer's organization. To ensure that all parties agree on the userpolicy 540, the user policy 540 can be stored in the linear sequence,such as the team linear sequence 310 in FIG. 3, and is guaranteed to bethe same for all users cooperating on a particular linear sequence. Anexample of a team policy rule is “only team admins can add new membersto a team.”

The application policy 550 can be defined per team 160, 170 in FIG. 1.The key difference between the application policy and other policies isthat the application policy operates after any cyphertext has beendecrypted. Consequently, the application policy cannot be checked by theserver. The application policy may not record authority, and can specifylow level rules such as “two files cannot have the same name.” Theapplication policy 550 can encode rules to resolve low-level conflictssuch as “if two files have the same name, the second file is ignored.”Policies, including the system policy 530, the user policy 540 and/orthe application policy 550, can be fixed in the program or managed usingthe linear sequences, such as team linear sequence 200 and space linearsequence 210 in FIG. 2.

FIG. 6 shows various cryptographic IDs that can exist within the system.Identities form the foundation of the security. Identities arerepresented by cryptographic identification (ID), such as asymmetric keypairs generated off-line using RSA, DH or other asymmetric algorithms.The public-key from the asymmetric key pair is used as the cryptographicidentity of the entity, while the private-key from the asymmetric keypair is known only to the entity. The off-line generation of the rootasymmetric key pairs protects the key pair from being compromised by abad actor. Device keys can be generated online but may be stored in ahardware security module (HSM).

A cryptographic ID, such as a cryptographic device ID or cryptographicuser ID, represents a single entity in the system, such as a device or auser, respectively. Consequently, the identity established using thecryptographic ID is globally distinct. In an embodiment, users areunique across teams even if no administrators distinguish them. Evenbetween non-cooperating groups, such as teams that do not share anymembers, the identity established using the cryptographic ID remainsglobally distinct.

The cryptographic user IDs can be used to sign/authorize device keyswhich are used operationally in the system. Devices can usecryptographic device IDs, which can include three keys types:administrative signing keys, message signing keys, and device encryptionkey. All of these key types are asymmetric key pairs and can be managedoutside of the application, in an operating system (OS) keys store or ahardware security module (HSM).

The identity certificate 600 can be deterministically generated from arecovery secret, allowing efficient hand transcription of the recoverysecret when provisioning a new device.

The administrative signing key 610 can be used in high-risk operationsand can require proof of user presence for any signing request. Examplesof the high-risk operations are adding users or changing permissions.

The message signing key 620 can be used to sign most data transmitted bythe device 110-160 in FIG. 1 and does not require proof of presence. Anexample use of the message signing key 620 is to sign messages sent in achat, or to sign files to be uploaded.

The device encryption key 630 can be used when sending a confidentialmessage to the device is necessary. The device encryption key 630 can berotated often to provide for forward secrecy for device to devicecommunications.

FIG. 7 shows how a block can be distributed to multiple devices. Devices700, 710, 720 can belong to the same space and/or team. They all canhave a copy of the linear sequence 730. When one of the devices, such asdevice 700, adds a new block 740 to the linear sequence 700, the device700 sends the new block 740 to the server 750.

The server 750 also has a copy of the linear sequence 730. The server750 can compute whether the block 740 is valid by computing whether theuser has the authority to perform the operation represented in the block740. To determine whether the user has the authority, the server 750 cancompute the authority from the linear sequence 730. The authoritycomputation is explained below.

Once the server 750 verifies that the block is valid, the server candistribute the block 740 to the devices 710, 720, which in turn can alsocompute whether the block 740 is valid based on the authority recordedin the linear sequence 730. If the device 710, 720 determines that theblock is not valid, the device can shut down because likely a breach ofthe system has occurred.

The devices 700, 710, 720 can share encrypted data 760, if they are inthe same space. The encrypted data 760 is encrypted using at least onecryptographic key, such as a confidential session key, explained below.Different devices 700, 710, 720 can have different authority to theencrypted data 760 such as read-only, write-only, and read and writeauthority.

The server 750 can also store the encrypted confidential data 760,however the server 750 does not store any of the cryptographic keys,including the confidential session key. The server 750 does not have anyauthority to the encrypted data 760. The server 750 has a copy of theencrypted data 750 to ensure availability of the data. For example, ifthe devices 700, 710 are off-line, and the device 720, as a newly addedmember of the space, requests the encrypted confidential data 760, theserver 750 can provide the encrypted confidential data 760 to the device720, even if the devices 700, 710 are off-line.

FIG. 8 shows a linear sequence containing blocks. The linear sequence800 contains at least blocks 810, 820, 830. Block 810 contains multipleevents 812, 814, while block 820 contains events 822, 824. Block 810 isthe initial block in the linear sequence 800 and contains the policy 816defining authority for the linear sequence 800. Each event in thesubsequent blocks, such as block 820, can be verified to ensure that theevent 822, 824 is consistent with the policy 816.

Each block subsequent to the initial block, such as block 820, includesthe cryptographic hash 826 of the previous block, which for block 820would be the hash of block 810. By including the cryptographic hash ofthe previous block, the ordering of the blocks in the linear sequence800 can be guaranteed, and a reordering or editing of existing blocks,and/or an insertion of new blocks within the linear sequence 800 can bedetected and automatically rejected.

The linear sequence 800 does not require a proof of work to verify thevalidity of the block, because the linear sequence 800 is a linearsequence, without any branching. Further, when a block is added to thelist, the block's validity has been checked to comply with the policyand authority recorded in the linear sequence 800, and the block cannotbe deleted. In other words, the order list 800 cannot be rolled back.

Within the initial block 810, event 812 establishes Alice as the user.The event is signed by Alice, meaning that Alice uses her private-key toencrypt the statement “Alice is a user.” To verify that Alice is trulyrequesting to be established as a user, a processor can verify thesigned statement “Alice is a user,” using Alice's public-key and ifverification succeeded the processor can know that Alice has trulyrequested to establish the user.

Event 814 establishes Alice as an administrator. Similarly, the event issigned and the processor can verify Alice's identity, as explainedabove. Because block 810 is the initial block, the policy 816 for thelinear sequence is established. For example, policy 816 can state “onlyadministrators can add users.” Once block 810 has been committed to thelinear sequence 800, the effective roles of the system are that Alice isan administrator and Alice is a user.

Event 822 in block 820 establishes that Bob is a user. To computewhether Alice has the authority to add the user, the processor can checkthe policy 816 and Alice's role in the system established by events 812,814. Because the policy specifies that only administrators can addusers, the processor checks whether Alice is an administrator. Uponverifying that Alice is an administrator, the processor can verify thatAlice has the authority to add Bob as a user. Each event subsequent tothe events contained in the initial block 812, 814, can be checkedagainst the policy 816, and the policy authorizing the event can berecorded. For example, for event 822, block 820 can point to the policystating that “only administrators can add users,” and a processor cancheck that there is a fact stored in a fact database that “Alice is anadministrator.”

Event 824 adds Carol as a user and must also be signed by Alice, asexplained above. Event 822 can also point to the policy that authorizedthe event, namely the policy stating “only administrators can add users”which is supported by the fact that “Alice is an administrator.” Thehash 826 creates a linear sequence of blocks 810, 820. After block 820has been committed to the linear sequence 800, the effective roles inthe system are that Alice is an administrator, and Alice, Bob, and Carolare users.

Other roles can be defined within the team such as legal, technical,sales etc. Each role can be granted access to a corresponding spacetype. For example, if Alice has role of “legal,” Alice can be grantedaccess to all spaces that have type “legal.” If Alice's “legal” role isrevoked, Alice can automatically lose access to the spaces that havetype “legal.”

FIG. 9 shows a team linear sequence and a space linear sequence. In thisexample, the team linear sequence 900 and the block linear sequencecontain blocks that include only one event. The team linear sequence 900is initialized with the initial block 910 and using connection 915linked to the policy 920, which establishes the policy for the team andany spaces. In block 930, Alice adds Bob as a user, and this event canbe linked, using connection 935, to the policy 920 that authorizes it.

In block 940, Bob creates space “planning,” and the event is linked tothe policy 920 to ensure that Bob as the user has the authority tocreate a space. By default, only the creator of the space is grantedadministrative authority to the space on the space linear sequence 970.If policy 920 authorizes users to create spaces, the block 930 isvalidated, the event is linked using connection 945 to the policy 920,and the block 940 is added to the team linear sequence 900. When Bobcreates space “planning,” space linear sequence 970 is established, withthe initial block 980 pointing to block 940 to indicate that the listwas created after block 940, but before block 950, explained below.

In block 950, Alice limits space creation to administrators. This actionchanges the policy 920. To verify whether block 950 is valid, aprocessor needs to check the policy 920 to see if the policy allowsadministrators to modify the policy. If the policy 920 allowsadministrators to modify the policy, the event is linked, usingconnection 955, to a portion of policy 920 that allows administrators tomodify the policy, and the new policy 925 is established. Even thoughafter block 950, Bob cannot create a space, because Bob had theauthority in block 942 to create the space, the space that Bob createdis valid. In block 960, Alice adds Carol, and the event is checkedagainst the new policy 925. Once the event is approved as authorized bythe new policy 925, the connection 965 is established to that portion ofthe new policy 925 that authorizes the event.

In block 990 of the space linear sequence 970, Bob adds Carol as a user.To verify whether block 990 is valid, the processor needs to check thenew policy 925 to see if policy 925 allows space users to add otherspace users. The policy 925 allows users to add users, and the event islinked, using connection 995, to a portion of the policy 925 thatauthorizes the event.

As explained earlier, only team members can be added to the space. IfBob attempts to add Carol prior to the block 950, the processor wouldnot authorize the addition of the block 990, because after checking thefact base and/or the team linear sequence 900, the processor candetermine that Carol is not a member of the team. However, if Bobattempts to add Carol to the space linear sequence 970 after block 960,the processor will authorize the addition of block 990, because thepolicy allows space users to add space users, and because Carol is amember of the team.

FIGS. 10A-B show authority computation in case a malicious actor triesto infiltrate the system. This example illustrates how a compromise ofthe server 1000 does not compromise the devices 1010, 1020, 1030 becauseeach device 1010-1030 independently checks and guarantees a validity ofthe linear sequence 1040 and the authority recorded in the linearsequence 1040.

If the server 1000 is compromised, for example, by a malicious serveradministrator who coerces the server 1000 into incorrectly verifying anddistributing a fraudulent block 1050 to the devices 1010-1030, eachdevice 1010-1030 can independently verify the validity of the block1050.

In FIG. 10B, each device 1010-1030 can independently verify that thehash 1060 of the last block in the linear sequence 1040 is valid. Eachdevice 1010-1030 can verify that user is a valid role. Each device1010-1030 can verify that Mal's signature is valid because, prior tosubmitting block 1050, Mal has requested that the server 1000 generate apublic-key and a private-key for him and distribute the public-keys tothe devices 1010-1030. However, the device 1010-1030 can determine thatblock 1050 is not valid because, according to system policy, onlyexisting members, such as administrators or users, can add new users,and Mal is not an administrator or a user. Because the block 1050 doesnot satisfy policy, all the devices 1010-1030 can reject the block 1050.In addition, the devices 1010-1030 can shut down once an invalidtransaction is received from the server 1000, because the devices1010-1030 can conclude that the server 1000 has been compromised.

FIG. 11A-C show how access to encrypted data can be controlled uponauthority revocation. Devices 1100, 1110, 1120 can share encrypted data1130, by, for example, being part of the same space. The encrypted data1130 can be encrypted using an Advanced Encryption Standard (AES), asymmetric-key algorithm using the same key for both encrypting anddecrypting the data. The encrypted confidential data 1130 can be storedon the devices 1100-1120 and the server 1140. The AES key can be knownonly to the devices 1100-1120 that have the authority to access theencrypted data 1130.

Assuming Alice is an administrator and has the authority to removeusers, Alice can submit a block 1150 to the server, that states “Carolis not a user,” thus revoking Carol's authority to any future encrypteddata shared between Alice and Bob. The server 1140 can distribute theblock 1150 to all the devices 1110-1120, as seen in FIG. 11B.

Upon validation of the block 1150, by the devices 1110-1120, Carol andher device 1120 lose the authority to access any future encrypted data.To ensure that Carol and her device 1120 cannot access any futureencrypted data shared between Alice and Bob, devices 1100, 1110 generatea new channel session key.

The new channel session key can be generated using the cryptographicmethods such as elliptic curve cryptography, for example, using a P-384elliptic curve. The channel session key can be generated using secretkey generation materials 1170, such as domain parameters in the case ofelliptic curve cryptography. The domain parameters can include theconstants A, B defining the elliptic curve Y²=X³+AX+B.

The new group of devices that share the key is computed based on thelinear sequence 1160. The secret key generation material 1170 isencrypted using each of the public-keys of an asymmetric cryptographicalgorithm belonging to the devices remaining in the new group ofdevices. The encrypted secret key generation materials 1170 aredistributed to all the devices in the group. The devices 1100, 1110 canuse their own private-keys of the asymmetric cryptographic algorithm todecrypt the received encrypted message. As a result, only devices 1100,1110 having the private key corresponding to the public-key used inencryption can calculate the new channel session key.

Devices 1100, 1110 receiving the secret key generation materials 1170can compute a private portion 1172 of the channel session key and apublic portion 1174 of the channel session key, and can record thepublic portion 1174 of the channel session key to the linear sequence1160. As a result of committing the public portion 1174 of the channelsession key to the linear sequence 1160, a client having an access tothe linear sequence 1160 can access the public portion 1174 and havewrite-only access to the linear sequence 1160. The client cannot readany of the encrypted data associated with the linear sequence 1160,because the client does not have the secret key generation materials1170 and/or the private portion 1172 of the channel session key. Theprivate portion 1172 of the channel session key is not recorded in thelinear sequence 1160.

Because the linear sequence 1160 does not require proof of work, andduplicating the linear sequence 1160 can be computationally feasible, acompromised server 1140 can present two different linear sequences 1162,1164 to two groups of users, as seen in FIG. 11C. For example, thecompromised server 1140 can refuse to distribute block 1150 to device1120, thus leading the device 1120 to believe it is still in the groupand to attempt to share encrypted data 1190 of device 1120 with devices1100 and 1110. Consequently, a new channel session key 1180 can becomputed based on the hash of the last block 1150 in the linear sequence1160. For example, the new channel session key 1180 can be obtained byperforming HKDF (channel session key in FIG. 11B, hash of block 1150).As a result, since devices 1100 and 1110 do not share the same lastblock with the device 1120, device 1120 cannot compute the same channelsession key 1180.

In addition to the users of the same space Alice and Bob, a guest usercan be temporarily granted access to the encrypted data contained in thesame space as Alice and Bob. The guest user does not have access to theteam linear sequence 1160 and cannot validate authority of a user withinthe space linear sequence 1160. However, the guest user can stillnegotiate a channel session key with Alice and Bob and be granted atemporary access to the encrypted data 1130.

FIG. 12 is a flowchart of a method to manage, via a distributed ledger,authority separately from access to encrypted data by one or moretrusted devices, wherein each of the trusted devices corresponds to atleast one cryptographic key-based identity. In step 1200, a processorcan create a block defining an authority of a user. The block caninclude a cryptographic user ID uniquely identifying the user and anauthority associated with the cryptographic user ID. The authority candefine at least an operation associated with the cryptographic user IDto perform on the encrypted data. The operation can include read-only,write-only, or read and write. Unlike a bitcoin ledger which requiresapproval to work, the block does not require an entry approving work,thus generation of the block is less processor intensive compared tobitcoin, which, on average, requires 10 minutes of processor time togenerate a proof of work for the block.

In step 1210, the processor can append the block to an end of a linearsequence, including multiple blocks defining an authority associatedwith the encrypted data, and preserves a membership and an ordering ofeach block in the multiple blocks. To preserve the membership of theblock, no block in the linear sequence can be deleted. In other words,deletion is not allowed operation on the linear sequence. To preserveordering of each block among multiple blocks, rollbacks are not anallowed operation of the linear sequence. In other words, the linearsequence cannot branch, and contents of a block in the linear sequencecannot be modified and/or edited once the block is added to the linearsequence. The prohibition of deletion and modification of blocks ensuresintegrity of the linear sequence. In other words, once a block is addedto the linear sequence, the block is permanently in the linear sequence.Further, before a block is added to the linear sequence, the contents ofthe block must be verified to ensure they are consistent with thepreceding blocks in the linear sequence.

In step 1220, the processor can receive a request to access theencrypted data. The request can include a cryptographic user IDassociated with the user making the request. Access to the encrypteddata can include read-only, write-only, or both read and write access.

In step 1230, the processor can determine whether the user making therequest has an authority to access the encrypted data by computing theauthority recorded in the linear sequence as shown in FIGS. 8, 9, and10A-B. To compute the authority, the processor can check the linearsequence from an initial block to a last block to determine user rolesand authority associated with each role, and to compare the request fromthe user to the user role. In other words, the processor can manageaccess to the encrypted data by the cryptographic user ID by checkingthat the access by the cryptographic user ID is permitted by theauthority recorded in the linear sequence.

In step 1240, the processor can grant access to the encrypted data tothe user making the request upon determining that the user making therequest has the authority to access the encrypted data.

The processor can create an initial block in the linear sequencedefining a policy specifying a role and an authority associated with therole. For example, the initial block 810 in FIG. 8 defines policy 816 inFIG. 8. Further, the processor can create the block in the linearsequence defining a role associated with the cryptographic user ID. Theblock can be the initial block 810, as shown in FIG. 8 which, inaddition to defining policy, defines that Alice is an administrator inevent 814 in FIG. 8, or the block can be a subsequent block, such asblock 820 in FIG. 8, which defines Bob and Carol as users.

To preserve the ordering of each block in the multiple blocks, theprocessor can include a cryptographic hash (“hash”) of each previousblock in each subsequent block, thus enabling detection of any change inthe ordering sequence, as explained in FIG. 8. For example, theprocessor can compute a second cryptographic hash of data contained in asecond block in the multiple blocks. The second block can be the initialblock, or any block, in the linear sequence. The processor can store thesecond cryptographic hash within the second block, and can include thesecond cryptographic hash in data contained in a block subsequent to thesecond block.

To preserve the membership of blocks within the linear sequence, theprocessor can define a set of operations to be performed on the linearsequence, where any operation outside of the defined set cannot beperformed in the linear sequence. The defined set can exclude operationssuch as deletion, branching of the linear sequence, and/or modificationof data within the linear sequence.

To reduce the likelihood of a failure, such as corrupting the linearsequence and/or the encrypted data by a compromised central server, theprocessor can distribute the linear sequence to multiple devices. Eachdevice in the multiple devices can be cryptographically verified by acryptographic user ID associated with the linear sequence, as explainedin FIG. 2. For example, to add a device to the list of authorizeddevices, an already authorized cryptographic user ID needs to requestaccess for the device, as explained in FIG. 2. Upon receiving therequest, the processor can verify that the cryptographic user ID indeedmade the request by decrypting the request using the public-key of thecryptographic user ID. Upon verification, the processor can assign acryptographic device ID to the device.

Each device among the multiple devices having the cryptographic deviceID can independently verify the validity of a request based on theauthority computed based on the linear sequence, as explained in FIGS.10A-B. If a device cannot verify that the block is valid based on thecomputed authority, the device can refuse to add the block. Upon failureto verify, the device can shut down to prevent tampering with theencrypted data on the device.

The processor can define a team of cryptographic user IDs, forefficiency purposes, so that not all the cryptographic IDs have to besearched to find a group of people who can share encrypted data amongstthemselves. To create the team, the processor can create a team linearsequence including multiple blocks. The multiple blocks can include oneor more policy blocks, one or more profile blocks, and one or moreauthority blocks. The one or more policy blocks can define a policyestablishing a role and an authority associated with the role, the oneor more profile blocks can establish a cryptographic user ID and acryptographic device ID associated with the cryptographic user ID, andthe one or more authority blocks can define the role associated with thecryptographic user ID. The team linear sequence is an instance of, andhas the same properties as, the linear sequence described in thisapplication.

The policy recorded in the initial block of a linear sequence, such asthe team linear sequence, can be modified if the policy recorded in theinitial block permits modification. If the policy recorded in theinitial block does not permit modification, any block attempting tomodify the policy will not be verified by the multiple devices.

To modify the policy, the processor can obtain a request to modify thepolicy defined in the one or more policy blocks and a cryptographic IDof a user making the request. The processor can check whether thecryptographic user ID is authorized to modify the policy by determiningauthority associated with the cryptographic ID from the team linearsequence. Usually only administrators are allowed to modify the policy,and the processor can check whether the cryptographic user ID has a roleof an administrator or a user. If the cryptographic user ID has the roleof a user, the processor can refuse to verify the block. Upondetermining that the cryptographic user ID is authorized, the processorcan create a policy block specifying the modification and can append thepolicy block defining the modification to the end of the team linearsequence.

Once the processor defines the team, the processor can define a spacewithin the team, which has a subset of the team members that canprivately share encrypted data. The space membership can be the same asthe team membership or can be smaller than the team membership. Thespace is a virtual compartment defining encrypted data and access to theencrypted data. The space can include the encrypted data using acryptographic key known only to the members of the space.

To define the space the processor can represent the members and theencrypted data by creating a space linear sequence. For efficiency, thespace linear sequence can be subdivided into multiple linear sequences.For example, the space linear sequence can be subdivided into anauthority linear sequence, and the encrypted data linear sequence. Theauthority linear sequence can define a role within the space of thecryptographic user ID. The cryptographic user ID is a member of thespace and the role is consistent with the policy defined in the one ormore policy blocks of the team. The encrypted data linear sequence canrecord operations performed on the encrypted data such as addition,deletion or modification of at least a portion of the encrypted data.

The encrypted data can include multiple types of encrypted data such asfiles, emails, messages, etc. The processor can create a linear sequencefor each of the encrypted data types. So, instead of creating oneencrypted data linear sequence, the processor can create a linearsequence for the files, a linear sequence for the emails and a linearsequence for the messages.

By creating a separate linear sequences for authority and for each typeof encrypted data, the processor can speed up the computation ofauthority because to compute the authority, the processor need onlyexamine the linear sequence of blocks containing data pertaining toauthority, as opposed to examining linear sequence containing authorityblocks as well as encrypted data blocks. Assuming that there are as manyauthority blocks as encrypted data blocks, by splitting up the spacelinear list into the authority linear list and encrypted data linearlist, the processor can speed up the computation of authority by afactor of two. Similarly, the processor can speed up retrieval ofencrypted data by approximately a factor of 2, because to retrieve theencrypted data, the processor need only examine the encrypted datalinear sequence, as opposed to linear sequence containing both encrypteddata blocks and the authority blocks.

The processor can revoke membership of a cryptographic user IDassociated with the space. When membership is revoked, the cryptographicuser ID must be prevented from accessing and encrypted data sharedwithin the space after the revocation of cryptographic user IDsmembership. To prevent the cryptographic user ID from accessingencrypted data added to the space after the revocation, the processorcan generate a cryptographic session key unknown to the cryptographicuser ID whose membership has been revoked, and can encrypt the encrypteddata added to the space after the revocation using the cryptographicsession key. The data contained in space prior to the revocation canalso be encrypted using the new cryptographic session key.

The new cryptographic session key can be an AES key computed using thefollowing 4 steps. In step 1, the AES key can be computed using ellipticcurve algorithm such as P-384. In step 2, the remaining group of devicesis computed from the space linear sequence, for example, the authoritylinear sequence within the space. In step 3, the AES key is encryptedusing a public device key of each device still in the space, and theencrypted AES key is distributed to each device within the space. Eachdevice can decrypt encrypted AES key because each device knows its ownprivate device key. Since no other devices know the private-key of thedevice, no eavesdroppers can decrypt the encrypted AES key. In step 4, amessage encrypted using the AES key can be distributed to the deviceswithin the space to ensure that everybody can decrypt the message.

In some instances, such as described in FIG. 11 C, the computation ofthe session key can include an additional step performed before step 3,in which the computation of the session key also includes acryptographic hash of the last block in the space linear sequence, suchas the authority linear sequence of the space. Specifically, once theAES key is computed in step 1, to generate the final key an additionalstep of combining the AES key and the cryptographic hash of the lastblock can be performed. The combination can be computed using the HKDFcryptographic function which takes his arguments the AES key and thecryptographic hash of the last block to produce the final key. The finalkey is then encrypted and distributed to all the devices.

In addition to computing the new session key once a member is removedfrom the list, the new session key can be computed when a new member isadded, and the intent is to prevent the member from accessing theencrypted data shared within the space prior to the member joining.

The processor can enable a linear ordering of the team linear sequencein the space linear sequence by establishing a temporal relationshipbetween multiple team blocks belonging to the team linear sequence andmultiple space blocks belonging to the space linear sequence, asexplained in FIG. 3. There can be various types of temporalrelationships, such as a space block can be bound to a team blockimmediately preceding the space block, or the space block can be boundto a team block immediately succeeding the space block, etc.Establishing the linear order is important in authority computation aswell as auditing.

For example, to determine the authority, reference needs to be made tothe current policy defined in the team space at a time prior to theaddition of the block. In another example, when performing auditing ofthe linear sequences, to determine whether a block was correctly addedto a space linear sequence, the current authority needs to be computedwhich can be partially defined on the team linear sequence. To determinethe current policy, a linear order of the blocks within the space linearsequence and the team linear sequence needs to be determined, so thatthe authority recorded in the team list prior to addition of a block canbe computed.

Consequently, every time a block is added to the space linear sequence,the block is bound to the team linear sequence to determine the linearorder between the team linear sequence and the space linear sequence.The linear order between two space linear sequences does not need to beestablished because the authority within the one space linear sequencedoes not affect the authority within the other space linear sequence.

FIG. 13 is a flowchart of a method to manage access to encrypted datausing a distributed ledger. In step 1300, a processor can manage accessto the encrypted data by checking that the access is permitted by anauthority recorded in a linear sequence including multiple blocksarranged, where an initial block in the linear sequence defines a policyspecifying a role and an authority associated with the role.

In step 1310, the processor can preserve a validity of the authorityrecorded in the linear sequence by cryptographically identifying a userassociated with the linear sequence, thus preventing an authorized userfrom accessing the linear sequence. Prior to adding a block associatedwith a user authority to the multiple blocks, the processor can checkthe linear sequence to ensure the user authority is consistent with thepolicy. Upon ensuring that the user authority is consistent with thepolicy, the processor can add the block associated with the userauthority to the multiple blocks.

The processor can determine a user role associated with the user, anauthority associated with the user role and can ensure the userauthority associated with the block is within the limits of theauthority associated with the user role.

For example, a block to be added to the sequence can request amodification of the policy. Prior to adding the block to the sequence,the processor can check whether the policy permits verification, andwhat role can modify the policy. For example, the policy can state thatthe policy can be modified but that only an administrator can modify thepolicy. If that is the case, the processor can check whether the userrequesting modification is an administrator or not.

To prevent unauthorized access to the data by a compromised centralserver, the processor can distribute a linear sequence to multipledevices associated with multiple users, wherein each device in themultiple devices is cryptographically authenticated by a user in themultiple users. The determination whether to add a block to the linearsequence can be made independently by each of the devices, instead ofbeing made by the central server, which creates a single point offailure.

The processor can authenticate each user using a cryptographic user ID,which can be a public-key generated using an asymmetric cryptographicalgorithm. The cryptographic user ID can be a string of 2,048 bits. Theasymmetric cryptographic algorithm can be RSA or DH, and can generatetwo keys, a public-key and a private-key. The processor can provide afirst key (i.e., the private-key) in the asymmetric cryptographic keypair only to the user, and the cryptographic user ID (i.e., thepublic-key) in the asymmetric cryptographic key pair to multiple usersinto the whole system. The processor can use the public-key is a way toidentify the user throughout the system. As a result, the user canassume different names in different teams or spaces, and the variousnames can be tied to one cryptographic user ID.

For example, to verify the user's identity, the processor can receive atext message and the text message can be signed using a private-key ofthe user. To verify the user's identity, the processor can use theuser's public-key (i.e., the cryptographic user ID) to reverse thesigning process. The processor can then compare the text message and themessage obtained by reversing the signing process. If the text messageand the message obtained by reversing the signing process are an exactmatch, the processor can verify the user's identity. Otherwise, theprocessor cannot verify the user's identity.

For efficiency purposes, the processor can create a team. To create ateam the processor can obtain multiple cryptographic user IDsidentifying multiple users. The processor can create the linear sequencecomprising the multiple blocks arranged in the linear sequence, wherethe initial block in the linear sequence defines the policy specifyingthe role and the authority associated with the role, and where a blockin the multiple blocks defines a role associated with a cryptographicuser ID in the multiple cryptographic user IDs identifying a user in themultiple users.

To create a space within the team, the processor does not have to searchall the cryptographic IDs in the system and can only search thecryptographic IDs contained in the team, thus preserving CPU cycles. Forexample, if a team contains 10 users, the whole system contains tens ofthousands of users, the number of processor cycles used to create thespace is reduced by approximately 1,000. The space can contain a subsetof the cryptographic user IDs of the team. The space can include thedata encrypted using a cryptographic key known only to the members ofthe space. The space can include a space linear sequence representingthe members and the encrypted data.

As explained in this application, the space linear sequence can containtwo or more sub-sequences for efficiency reasons. The space linearsequence can include an authority linear sequence containing blocksmodifying the authority within the system, such as adding or removingusers and/or administrators. Encrypted data linear sequence can includethe linear sequence adding, deleting, and modifying encrypted datawithin the system. Encrypted data linear sequence can be furthersubdivided into multiple linear sequences depending on the type of theencrypted data, such as files and/or messages.

The team linear sequence, the space linear sequences, and the encrypteddata can be stored in a memory configured to be continuously availableto one or more computers over a network, such as the central server. So,in case most of the devices within the space are off-line, a device inthe space can request encrypted data and/or can add a block to the spaceordered sequence from the central server.

Computer

FIG. 14 is a diagrammatic representation of a machine in the exampleform of a computer system 1400 within which a set of instructions, forcausing the machine to perform any one or more of the methodologies ormodules discussed herein, may be executed.

In the example of FIG. 14, the computer system 1400 includes aprocessor, memory, non-volatile memory, and an interface device. Variouscommon components (e.g., cache memory) are omitted for illustrativesimplicity. The computer system 1400 is intended to illustrate ahardware device on which any of the components described in the exampleof FIGS. 1-13 (and any other components described in this specification)can be implemented. The computer system 1400 can be of any applicableknown or convenient type. The components of the computer system 1400 canbe coupled together via a bus or through some other known or convenientdevice.

The computer system 1400 can represent the server such as 100 in FIG. 1,750 in FIG. 7, 1000 and FIG. 10 A, 1140 in FIGS. 11 A-C. The computersystem 1400 can represent the devices, such as 110-116 FIG. 1, 700-720in FIG. 7, 1010-1030 in FIG. 10 A, 1100-1120 in FIGS. 11 A-11 C. Theprocessor of the system 1400 can perform the various methods andinstructions described in this application. The main memory, nonvolatilememory, and/or the drive unit of the system 1400 can store theinstructions to be performed by the processor. The devices 1110-1160,700-720, 1010-1030, 1100-1120, and the processor 100, 750, 1000, 1140can communicate with each other using the network interface device ofthe system 1400.

This disclosure contemplates the computer system 1400 taking anysuitable physical form. As example and not by way of limitation,computer system 1400 may be an embedded computer system, asystem-on-chip (SOC), a single-board computer system (SBC) (such as, forexample, a computer-on-module (COM) or system-on-module (SOM)), adesktop computer system, a laptop or notebook computer system, aninteractive kiosk, a mainframe, a mesh of computer systems, a mobiletelephone, a personal digital assistant (PDA), a server, or acombination of two or more of these. Where appropriate, computer system1400 may include one or more computer systems 1400; be unitary ordistributed; span multiple locations; span multiple machines; or residein a cloud, which may include one or more cloud components in one ormore networks. Where appropriate, one or more computer systems 1400 mayperform without substantial spatial or temporal limitation one or moresteps of one or more methods described or illustrated herein. As anexample and not by way of limitation, one or more computer systems 1400may perform in real time or in batch mode one or more steps of one ormore methods described or illustrated herein. One or more computersystems 1400 may perform at different times or at different locationsone or more steps of one or more methods described or illustratedherein, where appropriate.

The processor may be, for example, a conventional microprocessor such asan Intel Pentium microprocessor or Motorola power PC microprocessor. Oneof skill in the relevant art will recognize that the terms“machine-readable (storage) medium” or “computer-readable (storage)medium” include any type of device that is accessible by the processor.

The memory is coupled to the processor by, for example, a bus. Thememory can include, by way of example but not limitation, random accessmemory (RAM), such as dynamic RAM (DRAM) and static RAM (SRAM). Thememory can be local, remote, or distributed.

The bus also couples the processor to the non-volatile memory and driveunit. The non-volatile memory is often a magnetic floppy or hard disk, amagnetic-optical disk, an optical disk, a read-only memory (ROM), suchas a CD-ROM, EPROM, or EEPROM, a magnetic or optical card, or anotherform of storage for large amounts of data. Some of this data is oftenwritten, by a direct memory access process, into memory during executionof software in the computer 1400. The non-volatile storage can be local,remote, or distributed. The non-volatile memory is optional becausesystems can be created with all applicable data available in memory. Atypical computer system will usually include at least a processor,memory, and a device (e.g., a bus) coupling the memory to the processor.

Software is typically stored in the non-volatile memory and/or the driveunit. Indeed, storing and entire large program in memory may not even bepossible. Nevertheless, it should be understood that for software torun, if necessary, it is moved to a computer readable locationappropriate for processing, and for illustrative purposes, that locationis referred to as the memory in this paper. Even when software is movedto the memory for execution, the processor will typically make use ofhardware registers to store values associated with the software, andlocal cache that, ideally, serves to speed up execution. As used herein,a software program is assumed to be stored at any known or convenientlocation (from non-volatile storage to hardware registers) when thesoftware program is referred to as “implemented in a computer-readablemedium.” A processor is considered to be “configured to execute aprogram” when at least one value associated with the program is storedin a register readable by the processor.

The bus also couples the processor to the network interface device. Theinterface can include one or more of a modem or network interface. Itwill be appreciated that a modem or network interface can be consideredto be part of the computer system 1400. The interface can include ananalog modem, isdn modem, cable modem, token ring interface, satellitetransmission interface (e.g. “direct PC”), or other interfaces forcoupling a computer system to other computer systems. The interface caninclude one or more input and/or output devices. The I/O devices caninclude, by way of example but not limitation, a keyboard, a mouse orother pointing device, disk drives, printers, a scanner, and other inputand/or output devices, including a display device. The display devicecan include, by way of example but not limitation, a cathode ray tube(CRT), liquid crystal display (LCD), or some other applicable known orconvenient display device. For simplicity, it is assumed thatcontrollers of any devices not depicted in the example of FIG. 14 residein the interface.

In operation, the computer system 1400 can be controlled by operatingsystem software that includes a file management system, such as a diskoperating system. One example of operating system software withassociated file management system software is the family of operatingsystems known as Windows® from Microsoft Corporation of Redmond, Wash.,and their associated file management systems. Another example ofoperating system software with its associated file management systemsoftware is the Linux™ operating system and its associated filemanagement system. The file management system is typically stored in thenon-volatile memory and/or drive unit and causes the processor toexecute the various acts required by the operating system to input andoutput data and to store data in the memory, including storing files onthe non-volatile memory and/or drive unit.

Some portions of the detailed description may be presented in terms ofalgorithms and symbolic representations of operations on data bitswithin a computer memory. These algorithmic descriptions andrepresentations are the means used by those skilled in the dataprocessing arts to most effectively convey the substance of their workto others skilled in the art. An algorithm is here, and generally,conceived to be a self-consistent sequence of operations leading to adesired result. The operations are those requiring physicalmanipulations of physical quantities. Usually, though not necessarily,these quantities take the form of electrical or magnetic signals capableof being stored, transferred, combined, compared, and otherwisemanipulated. It has proven convenient at times, principally for reasonsof common usage, to refer to these signals as bits, values, elements,symbols, characters, terms, numbers, or the like.

It should be borne in mind, however, that all of these and similar termsare to be associated with the appropriate physical quantities and aremerely convenient labels applied to these quantities. Unlessspecifically stated otherwise as apparent from the following discussion,it is appreciated that throughout the description, discussions utilizingterms such as “processing” or “computing” or “calculating” or“determining” or “displaying” or “generating” or the like, refer to theaction and processes of a computer system, or similar electroniccomputing device, that manipulates and transforms data represented asphysical (electronic) quantities within the computer system's registersand memories into other data similarly represented as physicalquantities within the computer system memories or registers or othersuch information storage, transmission or display devices.

The algorithms and displays presented herein are not inherently relatedto any particular computer or other apparatus. Various general purposesystems may be used with programs in accordance with the teachingsherein, or it may prove convenient to construct more specializedapparatus to perform the methods of some embodiments. The requiredstructure for a variety of these systems will appear from thedescription below. In addition, the techniques are not described withreference to any particular programming language, and variousembodiments may thus be implemented using a variety of programminglanguages.

In alternative embodiments, the machine operates as a standalone deviceor may be connected (e.g., networked) to other machines. In a networkeddeployment, the machine may operate in the capacity of a server or aclient machine in a client-server network environment, or as a peermachine in a peer-to-peer (or distributed) network environment.

The machine may be a server computer, a client computer, a personalcomputer (PC), a tablet PC, a laptop computer, a set-top box (STB), apersonal digital assistant (PDA), a cellular telephone, an iPhone, aBlackberry, a processor, a telephone, a web appliance, a network router,switch or bridge, or any machine capable of executing a set ofinstructions (sequential or otherwise) that specify actions to be takenby that machine.

While the machine-readable medium or machine-readable storage medium isshown in an exemplary embodiment to be a single medium, the term“machine-readable medium” and “machine-readable storage medium” shouldbe taken to include a single medium or multiple media (e.g., acentralized or distributed database, and/or associated caches andservers) that store the one or more sets of instructions. The term“machine-readable medium” and “machine-readable storage medium” shallalso be taken to include any medium that is capable of storing, encodingor carrying a set of instructions for execution by the machine and thatcause the machine to perform any one or more of the methodologies ormodules of the presently disclosed technique and innovation.

In general, the routines executed to implement the embodiments of thedisclosure, may be implemented as part of an operating system or aspecific application, component, program, object, module or sequence ofinstructions referred to as “computer programs.” The computer programstypically comprise one or more instructions set at various times invarious memory and storage devices in a computer, and that, when readand executed by one or more processing units or processors in acomputer, cause the computer to perform operations to execute elementsinvolving the various aspects of the disclosure.

Moreover, while embodiments have been described in the context of fullyfunctioning computers and computer systems, those skilled in the artwill appreciate that the various embodiments are capable of beingdistributed as a program product in a variety of forms, and that thedisclosure applies equally regardless of the particular type of machineor computer-readable media used to actually effect the distribution.

Further examples of machine-readable storage media, machine-readablemedia, or computer-readable (storage) media include but are not limitedto recordable type media such as volatile and non-volatile memorydevices, floppy and other removable disks, hard disk drives, opticaldisks (e.g., Compact Disk Read-Only Memory (CD ROMS), Digital VersatileDisks, (DVDs), etc.), among others, and transmission type media such asdigital and analog communication links.

In some circumstances, operation of a memory device, such as a change instate from a binary one to a binary zero or vice-versa, for example, maycomprise a transformation, such as a physical transformation. Withparticular types of memory devices, such a physical transformation maycomprise a physical transformation of an article to a different state orthing. For example, but without limitation, for some types of memorydevices, a change in state may involve an accumulation and storage ofcharge or a release of stored charge. Likewise, in other memory devices,a change of state may comprise a physical change or transformation inmagnetic orientation or a physical change or transformation in molecularstructure, such as from crystalline to amorphous or vice versa. Theforegoing is not intended to be an exhaustive list in which a change instate for a binary one to a binary zero or vice-versa in a memory devicemay comprise a transformation, such as a physical transformation.Rather, the foregoing is intended as illustrative examples.

A storage medium typically may be non-transitory or comprise anon-transitory device. In this context, a non-transitory storage mediummay include a device that is tangible, meaning that the device has aconcrete physical form, although the device may change its physicalstate. Thus, for example, non-transitory refers to a device remainingtangible despite this change in state.

Remarks

The language used in the specification has been principally selected forreadability and instructional purposes, and it may not have beenselected to delineate or circumscribe the inventive subject matter. Itis, therefore, intended that the scope of the invention be limited notby this Detailed Description, but rather by any claims that issue on anapplication based hereon. Accordingly, the disclosure of variousembodiments is intended to be illustrative, but not limiting, of thescope of the embodiments, which is set forth in the following claims.

1. A computer-implemented method to manage, via a distributed ledger,authority separately from access to a file system by one or more trusteddevices, wherein each of the trusted devices corresponds to at least oneunique key-based identity, the method comprising: creating an initialblock in a linear sequence comprising a plurality of blocks, the initialblock defining a policy specifying a role and an authority associatedwith the role; creating a block defining an authority of a user, theblock comprising a unique user ID identifying the user and a roleassociated with the unique user ID, wherein the role and the authorityassociated with the role is defined by the policy, the role defining atleast an operation associated with the unique user ID to perform on thefile system; appending the block to an end of the linear sequencedefining an authority associated with the file system and preserving amembership and an ordering of each block in the plurality of blocks;distributing the linear sequence to a plurality of authorized devices,wherein each device in the plurality of authorized devices is verifiedby at least one unique user ID in a plurality of unique user IDsassociated with the linear sequence; receiving a request to access thefile system comprising a unique user ID associated with a user makingthe request; independently determining by each authorized device in theplurality of authorized devices whether the unique user ID making therequest has an authority to access the file system by computing theauthority recorded in the linear sequence by checking the linearsequence from the initial block to a last block; and granting access tothe file system to the user making the request upon determining that theuser making the request has the authority to access the encrypted data.2. A computer-implemented method comprising: creating a block definingan authority of a user, the block comprising a cryptographic user IDidentifying the user and the authority associated with the cryptographicuser ID, the authority defining at least an operation associated withthe cryptographic user ID to perform on an encrypted data; appending theblock to an end of a linear sequence comprising a plurality of blocksdefining an authority associated with the encrypted data and preservinga membership and an ordering of each block in the plurality of blocks;receiving a request to access the encrypted data comprising acryptographic user ID associated with a user making the request;determining whether the user making the request has an authority toaccess the encrypted data by computing the authority recorded in thelinear sequence by checking the linear sequence from an initial block toa last block; and granting access to the encrypted data to the usermaking the request upon determining that the user making the request hasthe authority to access the encrypted data.
 3. The method of claim 2,comprising: creating the initial block in the linear sequence defining apolicy specifying a role and an authority associated with the role; andcreating the block in the linear sequence defining a role associatedwith the cryptographic user ID.
 4. The method of claim 2, saidpreserving the ordering of each block in the plurality of blockscomprising: computing a second cryptographic hash of data contained in asecond block in the plurality of blocks; storing the secondcryptographic hash within the second block; and including the secondcryptographic hash in data contained in a block subsequent to the secondblock.
 5. The method of claim 2, comprising reducing a likelihood of afailure by: distributing the linear sequence to a plurality ofauthorized devices, wherein each device in the plurality of authorizeddevices is cryptographically verified by the cryptographic user ID in aplurality of cryptographic user IDs associated with the linear sequence;and independently verifying a validity of the request by each authorizeddevice in the plurality of authorized devices based on the authoritycomputed based on the linear sequence.
 6. The method of claim 2,comprising: defining a team by creating a team linear sequencecomprising the plurality of blocks including one or more policy blocks,and one or more authority blocks, the one or more policy blocks defininga policy establishing a role and an authority associated with the role,and the one or more authority blocks defining the role associated withthe cryptographic user ID.
 7. The method of claim 6, the team linearsequence, comprising one or more profile blocks establishing thecryptographic user ID and a cryptographic device ID associated with thecryptographic user ID.
 8. The method of claim 6, comprising: obtaining arequest to modify the policy defined in the one or more policy blocksand a cryptographic ID of a user making the request; checking whetherthe cryptographic user ID is authorized to modify the policy bydetermining the authority associated with the cryptographic ID from theteam linear sequence; upon determining that the cryptographic user ID isauthorized, creating a policy block associated with the request tomodify the policy; and appending the policy block to the end of the teamlinear sequence.
 9. The method of claim 6, comprising: defining a spacewhose members are a subset of members of the team, the space comprisingthe encrypted data encrypted using a cryptographic key known only to themembers of the space, said defining of the space comprising representingthe members and the encrypted data by creating a space linear sequence.10. The method of claim 9, said creating the space linear sequencecomprising: creating an authority linear sequence defining a role withinthe space of the cryptographic user ID, wherein the cryptographic userID is a member of the space and the role is consistent with the policydefined in the one or more policy blocks of the team; and creating anencrypted data linear sequence recording operations performed on theencrypted data comprising addition, deletion, or modification of atleast a portion of the encrypted data.
 11. The method of claim 9,comprising: revoking membership of a cryptographic user ID associatedwith the space; preventing the cryptographic user ID from accessingencrypted data added to the space after the revocation by generating acryptographic session key unknown to the cryptographic user ID whosemembership has been revoked; and encrypting the encrypted data added tothe space after the revocation using the cryptographic session key. 12.The method of claim 11, said generating the cryptographic session keycomprising: generating a cryptographic hash of the last block in thespace linear sequence; and generating the cryptographic session key bycombining the cryptographic hash of the last block and the cryptographicsession key unknown to the cryptographic user ID whose membership hasbeen revoked.
 13. The method of claim 9, comprising: enabling a linearordering between the team linear sequence and the space linear sequenceby establishing a temporal relationship between a plurality of teamblocks belonging to the team linear sequence and a plurality of spaceblocks belonging to the space linear sequence.
 14. A system comprising:at least one processor; and memory coupled to the at least oneprocessor, the memory comprising computer executable instructions that,when executed by the at least one processor, performs a methodcomprising: managing access to encrypted data by checking that theaccess is permitted by an authority recorded in a linear sequencecomprising a plurality of blocks wherein an initial block in the linearsequence defines a policy specifying a role and an authority associatedwith the role; and preserving a validity of the authority recorded inthe linear sequence by: cryptographically identifying a user associatedwith the linear sequence, checking the linear sequence to ensure a userauthority associated with a block is consistent with the policy bydetermining a user role associated with the user, an authorityassociated with the user role and ensuring the user authority associatedwith the block is within limits of the authority associated with theuser role, and upon ensuring that the user authority is consistent withthe policy, adding the block associated with the user authority to theplurality of blocks.
 15. The system of claim 14, the processorperforming the method comprising: distributing the linear sequence to aplurality of devices associated with a plurality of users, wherein eachdevice in the plurality of devices is cryptographically authenticated bya user in the plurality of users.
 16. The system of claim 14, theprocessor performing the method comprising: generating an asymmetriccryptographic key pair for the user; providing a first key in theasymmetric cryptographic key pair only to the user, and a cryptographicuser ID in the asymmetric cryptographic key pair to a plurality ofusers; and identifying the user using the cryptographic user ID in theasymmetric cryptographic key pair.
 17. The system of claim 14, theprocessor performing the method comprising: obtaining a plurality ofcryptographic user IDs identifying a plurality of users; and creatingthe linear sequence comprising the plurality of blocks wherein theinitial block in the linear sequence defines the policy specifying therole and the authority associated with the role, and wherein the blockin the plurality of blocks defines a role associated with acryptographic user ID in the plurality of cryptographic user IDsidentifying the user in the plurality of users.
 18. The system of claim17, the processor performing the method comprising: defining a spacewhose members are a subset of the plurality of cryptographic user IDs,the space comprising at least a portion of the encrypted data encryptedusing a cryptographic key known only to the members of the space, saiddefining the space comprising representing the members and the encrypteddata by creating a space linear sequence.
 19. The system of claim 18,the computer executable instructions creating the space linear sequencecomprising: creating an authority linear sequence defining the roleassociated with the cryptographic user ID in the subset of the pluralityof cryptographic user IDs, wherein the role is consistent with thepolicy defined in the linear sequence; and creating one or moreencrypted data linear sequences based on a type of encrypted data, theone or more encrypted data linear sequences recording operationsperformed on the encrypted data comprising addition, deletion, ormodification of at least a part of the encrypted data.
 20. The system ofclaim 18, the processor performing the method comprising: revoking amembership of the cryptographic user ID in the subset of the pluralityof cryptographic user IDs; preventing the cryptographic user ID whosemembership has been revoked from accessing encrypted data added to thespace after the revocation by generating a cryptographic session keyunknown to the cryptographic user ID whose membership has been revoked;and encrypting the encrypted data added to the space after therevocation using the cryptographic session key.
 21. The system of claim20, the computer executable instructions generating the cryptographicsession key comprising: generating a cryptographic hash of a last blockin the space linear sequence; and generating the cryptographic sessionkey by combining the cryptographic hash of the last block and thecryptographic session key unknown to the cryptographic user ID whosemembership has been revoked.
 22. The system of claim 18, the processorperforming the method comprising: enabling a creation of a linear orderbetween the linear sequence and the space linear sequence byestablishing a temporal relationship between the plurality of blocksbelonging to the linear sequence and a plurality of space blocksbelonging to the space linear sequence.
 23. The system of claim 14, theprocessor performing the method comprising: enabling availability of thelinear sequence by storing a copy of the linear sequence in a memoryconfigured to be continuously available to one or more computers over anetwork.